Hi @jhl221123,

Thanks for the PR! This is a great step toward cleaning up the inconsistent use of set and with methods across the codebase.

A few comments and suggestions:

• In Fix(#2769): Modify the annotation processor in 2.x to give a warning if a plugin builder attribute does not have a public setter. #3195, we updated the PluginProcessor to throw a compilation error if a configuration field doesn't have a public set or with method. Could you update that check to only allow set methods going forward?

• Making that change will also help catch any remaining with methods that may have been missed. For example, AsyncWaitStrategyConfig and HtmlLayout still contain withers that should be removed.

• Minor: We follow a consistent documentation approach when deprecating methods:

  • Add @deprecated since <version> in the Javadoc of the deprecated method.
  • Add @since <version> to the new method replacing it.

  I should have mentioned that in the issue description, sorry for the additional work this causes.

• Minor: I noticed several methods include @SuppressWarnings("hiding") on parameters. This likely stems from a differing naming strategy among some contributors. Since we always use the same name for method parameters and their corresponding fields, these annotations aren't needed and just add noise. Could you remove them?

Thanks again for your work on this!

The BND Baseline plugins shows that you also need to bump the version of the org.apache.logging.log4j.core.async package to 2.26.0. You didn't modify it directly, but it gained additional methods through class inheritance.

Otherwise, this looks ready to be merged, thanks!